Skip to content

Conversation

bremerm31
Copy link
Contributor

Summary: Sometimes the triton backend may set a profiler to be different from the standard do_bench implmentation. For cuda this has no functional change, i.e. triton.runtime.driver.active.get_benchmarker() still points at do_bench.

Reviewed By: xuzhao9

Differential Revision: D84215437

Copy link

meta-codesync bot commented Oct 9, 2025

@bremerm31 has exported this pull request. If you are a Meta employee, you can view the originating Diff in D84215437.

bremerm31 added a commit to bremerm31/tritonbench that referenced this pull request Oct 9, 2025
…#537)

Summary:

Sometimes the triton backend may set a profiler to be different from the standard `do_bench` implmentation. For cuda this has no functional change, i.e. `triton.runtime.driver.active.get_benchmarker()` still points at `do_bench`.

Reviewed By: xuzhao9

Differential Revision: D84215437
@bremerm31 bremerm31 temporarily deployed to docker-s3-upload October 9, 2025 23:12 — with GitHub Actions Inactive
@bremerm31 bremerm31 temporarily deployed to docker-s3-upload October 9, 2025 23:12 — with GitHub Actions Inactive
@bremerm31 bremerm31 temporarily deployed to docker-s3-upload October 9, 2025 23:12 — with GitHub Actions Inactive
…#537)

Summary:

Sometimes the triton backend may set a profiler to be different from the standard `do_bench` implmentation. For cuda this has no functional change, i.e. `triton.runtime.driver.active.get_benchmarker()` still points at `do_bench`.

Reviewed By: xuzhao9

Differential Revision: D84215437
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants